Support for fields on record api and ordering within facet groups #253
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…g facet group names and values their priority (lower comes first). Facets without a priority go after the facets with explicit priority.
mirekys
approved these changes
Feb 26, 2024
|
@mesemus we need to fix failing tests before merging |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
record.record has an option "fields" to add any fields (dict field_name => field content) to record API. This can be used instead of "extra-code" to add fields on record (such as custom system fields, synthetic fields etc.)
Support for ordering within a facet group brings an option to specify the following ordering:
The propname will be the first facet for curator and the third one for other users